Lucene search

K
BroadcomBrocade Sannav

45 matches found

CVE
CVE
added 2024/07/09 12:15 p.m.4334 views

CVE-2024-3596

RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.

9CVSS6.4AI score0.00774EPSS
CVE
CVE
added 2022/01/18 4:15 p.m.701 views

CVE-2022-23302

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configura...

8.8CVSS9.3AI score0.72202EPSS
CVE
CVE
added 2022/01/18 4:15 p.m.589 views

CVE-2022-23305

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings int...

9.8CVSS9.4AI score0.14404EPSS
CVE
CVE
added 2024/04/19 5:15 a.m.134 views

CVE-2024-29964

Brocade SANnav versions before v2.3.0a do not correctly set permissions on files, including docker files. An unprivileged attacker who gains access to the server can read sensitive information from these files.

6.5CVSS5.3AI score0.00192EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.90 views

CVE-2024-29963

Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. Note: Brocade SANnav doesn't have access to remote Docker registries.

3.8CVSS8.5AI score0.00058EPSS
CVE
CVE
added 2024/11/21 11:15 a.m.85 views

CVE-2022-43937

Possible information exposure through log file vulnerability where sensitive fields are recorded in the debug-enabled logs when debugging is turned on in Brocade SANnav before 2.3.0 and 2.2.2a

5.7CVSS5.5AI score0.00055EPSS
CVE
CVE
added 2024/04/25 6:16 a.m.77 views

CVE-2024-4159

Brocade SANnav before v2.3.0a lacks protection mechanisms on port 2377/TCP and 7946/TCP, which could allow an unauthenticated attacker to sniff the SANnav Docker information.

5.3CVSS6.9AI score0.00263EPSS
CVE
CVE
added 2024/04/19 5:15 a.m.71 views

CVE-2024-29965

In Brocade SANnav before v2.3.1, and v2.3.0a, it is possible to back up the appliance from the web interface or the command line interface ("SSH"). The resulting backups are world-readable. A local attacker can recover backup files, restore them to a new malicious appliance, and retrieve the passwo...

6.8CVSS6.7AI score0.00172EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.67 views

CVE-2024-29960

In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. Any Brocade SAnnav VM based on the official OVA images is vulnerable to MITM over SSH. An attacker can decrypt and compromise the SSH traffic to the SANnav.

7.5CVSS8.4AI score0.00091EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.63 views

CVE-2019-16207

Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database and gain privileges.

7.8CVSS7.4AI score0.00044EPSS
CVE
CVE
added 2022/12/09 2:15 a.m.63 views

CVE-2022-33187

Brocade SANnav before v2.2.1 logs usernames and encoded passwords indebug-enabled logs. The vulnerability could allow an attacker with adminprivilege to read sensitive information.

5.5CVSS5AI score0.00137EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.62 views

CVE-2019-16206

The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the ‘trace’ and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information.

5.5CVSS5.4AI score0.00023EPSS
CVE
CVE
added 2024/04/19 5:15 a.m.62 views

CVE-2024-29966

Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. The vulnerability could allow an unauthenticated attacker full access to the Brocade SANnav appliance.

9.8CVSS8.5AI score0.00291EPSS
CVE
CVE
added 2024/04/19 5:15 a.m.62 views

CVE-2024-29967

In Brocade SANnav before Brocade SANnav v2.31 and v2.3.0a, it was observed that Docker instances inside the appliance have insecure mount points, allowing reading and writing access to sensitive files. The vulnerability could allow a sudo privileged user on the host OS to read and write access to t...

6CVSS6.4AI score0.00072EPSS
CVE
CVE
added 2024/11/21 11:15 a.m.59 views

CVE-2022-43933

An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where configuration secrets are logged in supportsave. Supportsave file is generated by an admin user troubleshooting the switch. The Logged information may include usernames and passwords, ...

4.4CVSS4.5AI score0.0003EPSS
CVE
CVE
added 2024/11/21 11:15 a.m.59 views

CVE-2022-43935

An information exposure through log file vulnerability exists in Brocade SANnav before Brocade SANnav 2.2.2, where Brocade Fabric OS Switch passwords and authorization IDs are printed in the embedded MLS DB file.

5.3CVSS5.1AI score0.0003EPSS
CVE
CVE
added 2024/04/17 10:15 p.m.57 views

CVE-2024-29952

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypted logs by manipulating command variables.

5.5CVSS6.6AI score0.00046EPSS
CVE
CVE
added 2024/04/25 6:16 a.m.57 views

CVE-2024-4161

In Brocade SANnav, before Brocade SANnav v2.3.0, syslog traffic receivedclear text. This could allow an unauthenticated, remote attacker tocapture sensitive information.

8.6CVSS6.8AI score0.0015EPSS
CVE
CVE
added 2024/11/21 11:15 a.m.56 views

CVE-2022-43936

Brocade SANnav versions before 2.2.2 log Brocade Fabric OS switch passwords when debugging is enabled.

6.8CVSS6.6AI score0.00067EPSS
CVE
CVE
added 2024/04/19 5:15 a.m.53 views

CVE-2024-29962

Brocade SANnav OVA before v2.3.1 and v2.3.0a have an insecure file permission setting that makes files world-readable. This could allow a local user without the required privileges to access sensitive information or a Java binary.

5.5CVSS6.2AI score0.00067EPSS
CVE
CVE
added 2024/05/08 2:15 a.m.52 views

CVE-2024-2860

The PostgreSQL implementation in Brocade SANnav versions before 2.3.0a is vulnerable to an incorrect local authentication flaw. An attacker accessing the VM where the Brocade SANnav is installed can gain access to sensitive data inside the PostgreSQL database.

7.8CVSS6.7AI score0.00057EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.52 views

CVE-2024-29957

When Brocade SANnav before v2.3.1 and v2.3.0a servers are configured in Disaster Recovery mode, the encryption key is stored in the DR log files. This could provide attackers with an additional, less-protected path to acquiring the encryption key.

7.5CVSS6.4AI score0.00211EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.50 views

CVE-2019-16205

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID. The vulnerability is due to an insufficiently random session ID for several post-authentication actions in the SANnav portal.

8.8CVSS8.5AI score0.00352EPSS
CVE
CVE
added 2024/11/21 11:15 a.m.47 views

CVE-2022-43934

Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095.

7.5CVSS6.5AI score0.0005EPSS
CVE
CVE
added 2024/04/17 10:15 p.m.47 views

CVE-2024-29955

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs.This could provide attackers with an additional, less-protected path to acquiring the encryption key.

5.5CVSS6.5AI score0.00091EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.47 views

CVE-2024-29958

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node. This could provide attackers an additional, less protected path to acquiring the encryption k...

7.5CVSS6.5AI score0.00245EPSS
CVE
CVE
added 2024/04/19 6:15 a.m.47 views

CVE-2024-29969

When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, TLS/SSL weak message authentication code ciphers are added by default for port 18082.

7.5CVSS7.1AI score0.00125EPSS
CVE
CVE
added 2024/04/25 8:15 a.m.47 views

CVE-2024-4173

A vulnerability in Brocade SANnav exposes Kafka in the wan interface. The vulnerability could allow an unauthenticated attacker to perform various attacks, including DOS against the Brocade SANnav.

9.8CVSS6.8AI score0.0015EPSS
CVE
CVE
added 2021/06/09 4:15 p.m.46 views

CVE-2020-15387

The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, and Brocade SANnav before v2.1.1 utilize keys of less than 2048 bits, which may be vulnerable to man-in-the-middle attacks and/or insecure SSH communications.

7.4CVSS7.3AI score0.00124EPSS
CVE
CVE
added 2024/04/17 8:15 p.m.46 views

CVE-2024-29951

Brocade SANnav before v2.3.1 and v2.3.0a uses the SHA-1 hash in internal SSH ports that are not open to remote connection.

5.7CVSS6.8AI score0.0005EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.46 views

CVE-2024-29959

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save.

8.6CVSS6.8AI score0.00245EPSS
CVE
CVE
added 2024/04/19 4:15 a.m.46 views

CVE-2024-29961

A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthenticated, remote attacker aware of the beh...

8.2CVSS8.5AI score0.00915EPSS
CVE
CVE
added 2024/04/17 7:15 p.m.44 views

CVE-2024-29950

The class FileTransfer implemented in Brocade SANnav before v2.3.1, v2.3.0a, uses the ssh-rsa signature scheme, which has a SHA-1 hash.The vulnerability could allow a remote, unauthenticated attacker to perform a man-in-the-middle attack.

7.5CVSS6.7AI score0.00129EPSS
CVE
CVE
added 2024/04/18 2:15 a.m.44 views

CVE-2024-29956

A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the Brocade SANnav password in clear text in supportsave logs when a user schedules a switch Supportsave from Brocade SANnav.

6.5CVSS6.9AI score0.00108EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.43 views

CVE-2019-16208

Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.).

7.5CVSS7.4AI score0.00081EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.43 views

CVE-2019-16210

Brocade SANnav versions before v2.0, logs plain text database connection password while triggering support save.

5.5CVSS5.6AI score0.00028EPSS
CVE
CVE
added 2021/06/09 3:15 p.m.42 views

CVE-2020-15382

Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password ‘passw0rd’ if a password is not provided for PostgreSQL at install-time.

7.2CVSS7.1AI score0.00273EPSS
CVE
CVE
added 2024/04/19 6:15 a.m.41 views

CVE-2024-29968

An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mode. SQL Table names, column names, and SQL queries are collected in DR standby Supportsave. This could allow authenticated users to access t...

7.7CVSS7.3AI score0.00216EPSS
CVE
CVE
added 2023/08/31 1:15 a.m.39 views

CVE-2023-31424

Brocade SANnav Web interface before Brocade SANnav v2.3.0 and v2.2.2aallows remote unauthenticated users to bypass web authentication andauthorization.

9.8CVSS8.8AI score0.00553EPSS
CVE
CVE
added 2019/11/08 6:15 p.m.36 views

CVE-2019-16209

A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could allow an attacker to perform a man-in-the-middle attack against Secure Sockets Layer(SSL)connections.

7.4CVSS7.2AI score0.00215EPSS
CVE
CVE
added 2020/09/25 2:15 p.m.36 views

CVE-2019-16212

A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP injection. The vulnerability could allow a remote attacker to bypass the authentication process.

8.8CVSS9.1AI score0.0015EPSS
CVE
CVE
added 2023/08/31 1:15 a.m.35 views

CVE-2023-31423

Possibleinformation exposure through log file vulnerability where sensitivefields are recorded in the configuration log without masking on BrocadeSANnav before v2.3.0 and 2.2.2a. Notes:To access the logs, the local attacker must have access to an already collected Brocade SANnav "supportsave"output...

5.7CVSS5.3AI score0.00055EPSS
CVE
CVE
added 2020/09/25 2:15 p.m.29 views

CVE-2019-16211

Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.

9.8CVSS9.4AI score0.00282EPSS
CVE
CVE
added 2021/06/09 4:15 p.m.26 views

CVE-2020-15379

Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due to a lack of proper validation, of the length of user-supplied data as name for custom field name.

7.5CVSS7.5AI score0.00449EPSS
CVE
CVE
added 2023/08/31 1:15 a.m.24 views

CVE-2023-31925

BrocadeSANnav before v2.3.0 and v2.2.2a stores SNMPv3 Authentication passwordsin plaintext. A privileged user could retrieve these credentials withknowledge and access to these log files. SNMPcredentials could be seen in SANnav SupportSave if the capture isperformed after an SNMP configuration fail...

6.5CVSS5.7AI score0.00039EPSS